When you specify table locking , a bulk update table - level lock is taken for the duration of the bulk - import operation 指定表锁定后，在大容量导入操作期间采取大容量更新表级锁定。
Intent locks , row locks , and page locks all count toward the escalation count , unless they are temporary table locks 除非属于临时表锁，否则意向锁、行锁和页锁都将计入升级统计中。
The database engine chooses the appropriate lock and can escalate the lock from a row or page lock to a table lock 数据库引擎将选择相应的锁，并且可以将锁从行锁或页锁升级到表锁。
Does not perform any allocation checks and must acquire shared table locks to perform table checks 运行dbcc checkfilegroup不会执行任何分配检查，并且必须获取共享表锁才能执行表检查。
The database engine does not escalate row or key - range locks to page locks , but escalates them directly to table locks 数据库引擎不会将行锁或键范围锁升级到页锁，而是将它们直接升级到表锁。
Does not perform any allocation or catalog checks and must acquire shared table locks to perform table checks 运行dbcc checkdb不会执行任何分配或目录检查，并且必须获取共享表锁才能执行表检查。
The dbcc commands use table locks instead of the internal database snapshots when the command is executed against the following 当针对以下对象执行dbcc命令时，该命令将使用表锁而不是内部数据库快照：
Takes page locks either where individual locks are ordinarily taken on rows or keys , or where a single table lock is ordinarily taken 在通常行或键采用单个锁的地方，或者通常采用单个表锁的地方，请采用页锁。
The database engine escalates row or page locks to table locks if the amount of memory used by lock objects exceeds one of the following conditions 如果锁对象使用的内存量超出下列条件之一，则数据库引擎将行锁或页锁升级为表锁：
In this case , an exclusive database lock is required to perform the allocation checks , and shared table locks are required to perform the table checks 在这种情况下，需要排他数据库锁才能执行分配检查，需要共享表锁才能执行表检查。
